POV-Ray : Newsgroups : povray.general : Scope of identifiers in nested Macros : Re: Scope of identifiers in nested Macros Server Time
3 Aug 2024 22:14:09 EDT (-0400)
  Re: Scope of identifiers in nested Macros  
From: Warp
Date: 3 Jan 2004 18:31:01
Message: <3ff750b5@news.povray.org>
Christopher James Huff <cja### [at] earthlinknet> wrote:
> >   How would #def be different from #local?

> It would give a warning or error when used on an existing variable.

  Wasn't #set for that? I'm confused.

> >   What's wrong with #local? It's certainly a whole lot more descriptive
> > than #def.

> And it's used. Changing it would break backwards compatibility.

  I don't understand what you are saying.

> I don't like this idea. One thing about C++ that I've never liked was 
> the way you couldn't tell by reading the call whether you were passing 
> by reference or by value.

  Currently you have only one option: By reference. And this is causing
confusion.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.